VBTRACE 2.0 

VBTrace is a utility program designed primarily to fill a void in the Visual Basic tool kit, namely the ability to obtain a listing of the procedures executed by a Visual Basic program in the order in which they are executed.  The standard step tracing provided with Visual Basic is fine for tracing code within a procedure, but is inadequate for tracing program flow from procedure to procedure or through idle time events such as SetFocus or input from the keyboard.  Using step tracing will, in many instances, actually change the order in which the procedures are executed.

With VBTrace you can easily:
 1) Spot procedures which are being called accidentally or unnecessarily,
 2) See the exact order in which procedures and events are executed.
 3) See why a particular form takes so long to load
 4) Know how many forms are loaded at any point in a program.
 5) Tell if a procedure is being called recursively.
 6) See which areas of your program use the most Windows resources.
 7) See when each form is actually loaded and unloaded.
 8) Track GDI, USER, and Global Memory usage from procedure to procedure.
 9) Track disk space usage.
10) Set and track an unlimited number of watch variables.
11) Monitor the value of arguments being passed to procedures.
12) Pinpoint cascade events.
13) Time a procedure or group of procedures.
14) Automatically add Error Code to each procedure in a project.
15) Add line numbers to each executable statement in a project. This is convenient for locating errors in compiled programs.
16) Generate a cross reference listing showing all global, form level, and procedure level variables being used in the program and where each is referenced. Also shown are any variables created but never referenced.
17) Generate a cross reference listing showing all procedures in the program and where each procedure is referenced. Also shown are any procedures which are never referenced in the program.
18) Backup the project.
19) Monitor GDI, USER, and global memory while developing your project in the Visual Basic environment.

There are times in your Visual Basic program when the user clicks, tabs, or Alt/keys and you have no idea which procedures are executed and in what order.  With VBTrace, you always know.


Please forward bug reports and suggestions to:

Chuck Stuart
cstuart@metronet.com
76560,51 on CIS
ChukStuart on AOL